Warp wrote:
> Alain <ele### [at] netscapenet> wrote:
>   The important thing, IMO, is that it doesn't hard-code that what is
> returned by the function is precisely a mesh. It should be more abstract
> than that.

Actually no.  I would want a mesh object to be able to load from mesh 
data types only (or be created on the fly in SDL like always)  I would 
never want a CSG union, light source, or bologna sandwich to be able to 
load into a mesh, for instance.

The POVMesh object should descend from a POVObject, just like a 
POVSphere, POVCylinder, POVBlob, POVUnion, etc.  But there should be no 
way that a POVCylinder would implement the loadfrom3DS() method.

Keep in mind that the point of this thread is not about things to do to 
the SDL to improve it (which should also happen), it's about decoupling 
the SDL from the back-end so that we can integrate with more powerful 
languages (along with the SDL).  The examples I gave were not how I 
think the SDL should look at all.  I was envisioning what the code would 
look like in a fully object-oriented language.


-- 
Bryan Valencia

"I'd rather live with false hope than with false despair."

Post a reply to this message